fix: accept conftest.py as alternative to context.py, document test separation#36
Merged
TheRealAgentK merged 2 commits intomasterfrom Apr 20, 2026
Merged
Conversation
…idation Integrations using pytest can use tests/conftest.py instead of the legacy tests/context.py for test import/fixture setup. The validator now accepts either file — at least one must be present.
…iles - Add 'Running Tests' section to LOCAL_DEVELOPMENT.md (unit vs integration) - Add run_tests.py step to CI table in LOCAL_DEVELOPMENT.md - Add 'Unit Tests Only' section to scripts/docs/run_tests.md - Add note to README.md that run_tests.py is unit-only - Update required files lists: tests/context.py or tests/conftest.py
TheRealAgentK
requested review from
NinosMan,
ProRedCat and
Shubhank-Jonnada
and removed request for
Shubhank-Jonnada
ProRedCat
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two changes: a validation fix and documentation updates, both supporting the automated testing work in autohive-integrations PR #250.
1. Fix: Accept
conftest.pyas alternative tocontext.pyProblem:
validate_integration.pyrequirestests/context.pyas a hard dependency. Integrations that have migrated to pytest usetests/conftest.pyinstead (for pytest fixture setup), and the validator fails with:Fix: The validator now accepts either
tests/context.py(legacy) ortests/conftest.py(pytest). At least one must be present.Files changed:
scripts/validate_integration.py— validation logicscripts/docs/validate_integration.md— updated checks tableINTEGRATION_CHECKLIST.md— addedconftest.pyto lint suppression tableContext: 84 of 86 integrations still use
context.py. Three integrations (hackernews, bitly, perplexity) have migrated toconftest.pyas part of the pytest testing prototype. This change is backwards-compatible — existing integrations are unaffected.2. Docs: Unit/integration test separation
Documents the two-tier testing approach established in the integrations repo:
test_*_unit.pytest_*_integration.py@pytest.mark.unit@pytest.mark.integrationrun_tests.py).env)Files changed:
LOCAL_DEVELOPMENT.md— added "Running Tests" section, addedrun_tests.pyto CI table (was missing), updated required files listREADME.md— added note thatrun_tests.pyis unit-only, updated required files listscripts/docs/run_tests.md— added "Unit Tests Only" section clarifying scope